Skip to content

chore: align pnpm 11 requirements across docs and workspace#257

Merged
toddgeist merged 2 commits into
mainfrom
feature/pnpm11-node-pnpm-requirements
May 12, 2026
Merged

chore: align pnpm 11 requirements across docs and workspace#257
toddgeist merged 2 commits into
mainfrom
feature/pnpm11-node-pnpm-requirements

Conversation

@toddgeist
Copy link
Copy Markdown
Contributor

@toddgeist toddgeist commented May 12, 2026 •
edited by coderabbitai Bot
Loading

Summary

  • update AI docs to reflect current Node and pnpm requirements
  • sync workspace/package metadata for pnpm 11 migration
  • adjust CLI integration tests for updated package manager expectations

Test plan

  • pnpm run ci (fails locally in docs build because __VARLOCK_ENV is not set in this environment)

Summary by CodeRabbit

  • Documentation

    • Added pnpm (version 11) to setup prerequisites and technical requirements.
    • Updated Node.js LTS version examples to include 26.x alongside 22.x and 24.x.

  • Chores

    • Updated pnpm to version 11.1.0 across project configuration files.

  • Tests

    • Updated test expectations and mocks to align with pnpm 11.1.0.

Review Change Stack

@toddgeist
chore: align pnpm 11 requirements across docs and workspace
ba096f6 
Document updated Node/pnpm requirements and synchronize workspace/test metadata for the pnpm 11 migration so contributors and CI use consistent tooling expectations.
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented May 12, 2026 •
edited
Loading

⚠️ No Changeset found

Latest commit: 6744f2d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel
Copy link
Copy Markdown

vercel Bot commented May 12, 2026 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
proofkit-docs Error Error May 12, 2026 5:00pm

Request Review

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 12, 2026 •
edited
Loading

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 9a86cdfa-f83d-406f-8ffd-8b7003a2460e

📥 Commits

Reviewing files that changed from the base of the PR and between ba096f6 and 6744f2d.

📒 Files selected for processing (1)
  • package.json
✅ Files skipped from review due to trivial changes (1)
  • package.json
📝 Walkthrough

Walkthrough

This PR upgrades pnpm from various pinned versions to 11.1.0 across the monorepo's package.json files, updates user documentation to reflect pnpm 11 and Node.js LTS prerequisites, and synchronizes test fixtures and mocks to expect the new version.

Changes

pnpm 11.1.0 Upgrade

Layer / File(s) Summary
Package manager version declarations
package.json, packages/registry/package.json		 Root and registry package.json files update their packageManager field to declare pnpm@11.1.0.
Getting started and technical requirements documentation
apps/docs/content/docs/ai/getting-started.mdx, apps/docs/content/docs/ai/technical-requirements.mdx		 User-facing prerequisites are updated to require Node.js supported LTS releases (22.x, 24.x, 26.x) and recommend pnpm version 11, with installation guidance and verification instructions.
Test fixtures and mocks for pnpm 11.1.0
packages/cli/tests/integration.test.ts, packages/cli/tests/live-git-init.test.ts, packages/cli/tests/test-layer.ts		 Test files update mocked pnpm version outputs and version assertions from 10.x releases to 11.1.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main objective of the changeset: updating documentation and package configuration files to align pnpm version 11 requirements across the codebase.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feature/pnpm11-node-pnpm-requirements

Comment @coderabbitai help to get the list of available commands and usage tips.

@toddgeist
Merge remote-tracking branch 'origin/main' into feature/pnpm11-node-p…
6744f2d 
…npm-requirements

# Conflicts:
#	package.json
@toddgeist toddgeist merged commit 8fc3562 into main May 12, 2026
10 of 13 checks passed
@toddgeist toddgeist deleted the feature/pnpm11-node-pnpm-requirements branch May 12, 2026 17:01
@coderabbitai coderabbitai Bot mentioned this pull request May 14, 2026
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@toddgeist